Summary

This PR migrates our release pipeline from using Lerna to Change Sets. The goal is to streamline the release process and leverage the flexibility and simplicity offered by Change Sets for versioning and publishing.

Changes Introduced

Added Change Sets

Integrated the Change Sets workflow for managing versioning and changelogs.
Configured Change Sets to align with our monorepo structure and release requirements.

Removed Lerna

Replaced Lerna commands and configurations with native npm/yarn workflows.
Removed Lerna-related dependencies and scripts from the codebase.

Updated CI/CD Pipeline

Modified the release pipeline to use Change Sets for version bumping and publishing.
Ensured compatibility with existing tooling and workflows.

Documentation Updates

Added guidance for using Change Sets in the contributing documentation.
Updated the release process documentation to reflect the removal of Lerna.

Motivation and context

How has this been tested?

• Test case 1

  1. Go here
  2. Do this

• Test case 2

  1. Go here
  2. Do this

• Did it pass in Desktop?

• Did it pass in Mobile?

• Did it pass in iPad?

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (minor updates related to the tooling or maintenance of the repository, does not impact compiled assets)

Checklist

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• If my change required a change to the documentation, I have updated the documentation in this pull request.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have reviewed at the Accessibility Practices for this feature, see: Aria Practices

Best practices

This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against main.